-
Notifications
You must be signed in to change notification settings - Fork 277
Restrict with_exprt to exactly three operands #8674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
f4a850d
to
d8fc072
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #8674 +/- ##
===========================================
+ Coverage 80.39% 80.40% +0.01%
===========================================
Files 1688 1688
Lines 207387 207380 -7
Branches 73 73
===========================================
+ Hits 166728 166744 +16
+ Misses 40659 40636 -23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Test results for this branch running on mldsa-native/main are all good. |
Test results for this branch running on mlkem-native/main are all good. |
This is in preparation of moving to 3-operand with-expressions: without intervening use of the simplifier some generated expressions could become unnecessarily large.
We cannot build a C++ API for the previous >= 3, odd-number operand variant. Alas, we ended up with various places in the code base silently ignoring additional operands, which led to wrong verification results in Kani as recent changes in CBMC made increasing use of the value set (which is one of the places that silently ignored additional operands). Resolves: diffblue#7272
d8fc072
to
fc5c5a0
Compare
This release addresses bugs in our handling of array-update ("with") expressions (via diffblue#8674) and gaps in our C17/C23 support (via diffblue#8673).
We cannot build a C++ API for the previous >= 3, odd-number operand variant. Alas, we ended up with various places in the code base silently ignoring additional operands, which led to wrong verification results in Kani as recent changes in CBMC made increasing use of the value set (which is one of the places that silently ignored additional operands).
This is an alternative solution over #8668: #8668 does also fix the wrong verification results, but does not resolve original design problem. This PR now seeks to address both the bug and the design problem, and does so by largely just removing code.
Resolves: #7272